Improve useVitePreprocess#173
Merged
Merged
Conversation
5 tasks
Member
|
What is the use case for this? Getting rid of the need to use |
Member
Author
|
Yes, and also when using css preprocessors like scss and stylus. Typescript would be handled with Vite's own esbuild instance so it would replace the need for There is still use cases for |
8feee11 to
72441c2
Compare
dominikg
approved these changes
Sep 29, 2021
Merged
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When enabling
useVitePreprocess,importsNotUsedAsValues: "preserve"won't be forced on the entire codebase, only in Svelte files.